Release 10.1A: OpenEdge Deployment:
Managing 4GL Applications

Code page compatibility

The Internal Code Page (-cpinternal) startup parameter determines the internal code page that OpenEdge uses in memory. The code page in which r-code is compiled and the internal code page of the session in which the r-code runs must be compatible. That is, the r-code code page must be either the internal code page, undefined, or convertible to the internal code page.

If the code page for a standard r-code procedure, from either an operating system file or a standard library, is not the same as the session’s internal code page, OpenEdge performs an in-memory conversion of the r-code text segments to the session’s internal code page.

Note: If you use the R-code In Code Page (-cprcodein) startup parameter to specify a code page for reading r-code text segments, OpenEdge reads the text segments as if they were written in that code page, even if the text segments were written in a different code page.

Since r-code procedures in memory-mapped procedure libraries are read-only, OpenEdge cannot perform an in-memory code page conversion of r-code text segments. If the code page of a memory-mapped r-code procedure is not compatible with the internal code page of the session in which the r-code runs, OpenEdge will not execute the r-code. It will report an error and stop execution.

For more information about the Internal Code Page (-cpinternal) and R-code In Code Page (-cprcodein) startup parameters, see OpenEdge Deployment: Startup Command and Parameter Reference .